This file will illustrate what can happen if there are certain low ASCII
characters present in a file.  While SaveText automatically finds and filters
out ASCII 9 tabs and ASCII 12 form-feeds, there are 29 other low ASCII
characters than could conceivably be found in a file and to automatically
check for them would impose too severe a speed penalty when they are usually
not present.

For example, here's a form feed character - .  If SaveText had not filtered
it out, the first of this sentence would not have appeared where it does.
 
And, here's 4 tabs -             right before this section of the sentence!

Since SaveText filtered those, nothing happened.  However, if you scroll down,
you will find that there are several more low ASCII characters buried in the
text.

Right now, press PgDown and notice how the sentence fragement 6 lines up
doesn't move - that's due to the vertical tab several lines below.



ASCII 13 carriage return - 

ASCII 0 null - 
ASCII 1 start of header - 

ASCII 2 start of transmission - 
ASCII 3 end of transmission - 
ASCII 4 end of text - 
ASCII 6 acknowledge - 

ASCII 8 backspace (5 of them!) - 


ASCII 11 vertical tab - 

ASCII 7 bell - 
   If you press the PgDown key, you hear a differently pitched beep - that's
   the ASCII 7 bell above being written to the screen.

ASCII 27 escape - 

ASCII 5 enquiry - 

ASCII 24 cancel - 

ASCII 14 - 

If you restart SaveText with the /n parameter and reload this file, notice
how all the ASCII character to right of the hyphens are missing - SaveText
has filtered them out!  For a rather extreme example, load ST.EXE - like it
says in the documentation, SaveText isn't designed to view binary files.